Programming content addressable memory

ABSTRACT

A memory system includes a memory device comprising a programming buffer and a content addressable memory (CAM) block. The memory system further includes a processing device that receives a plurality of data entries to be stored at the memory device and stores the plurality of data entries in a plurality of pages of the programming buffer, each of the plurality of pages of the programming buffer comprising a respective subset of the plurality of data entries. The processing device further initiates a conversion operation to copy the plurality of data entries from the programming buffer to the CAM block. The conversion operation includes reading respective portions of each data entry in each respective subset of the plurality of data entries from the plurality of pages of the programming buffer, and writing the respective portions to respective CAM pages of the CAM block.

RELATED APPLICATION

This application claims the benefit of U.S. Provisional Patent Application Ser. No. 63/201,554, filed May 4, 2021, the entire contents of which is hereby incorporated by reference herein.

TECHNICAL FIELD

Embodiments of the disclosure relate generally to memory sub-systems, and more specifically, relate to programming content addressable memory (CAM) in a memory sub-system

BACKGROUND

A memory sub-system can include one or more memory devices that store data. The memory devices can be, for example, non-volatile memory devices and volatile memory devices. In general, a host system can utilize a memory sub-system to store data at the memory devices and to retrieve data from the memory devices.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure will be understood more fully from the detailed description given below and from the accompanying drawings of various embodiments of the disclosure.

FIG. 1 illustrates an example computing system that includes a memory sub-system in accordance with some embodiments of the present disclosure.

FIG. 2 is a block diagram of a memory device in communication with a memory sub-system controller of a memory sub-system in accordance with some embodiments of the present disclosure.

FIG. 3 is a block diagram illustrating programming content addressable memory (CAM) in a memory sub-system in accordance with some embodiments of the present disclosure.

FIG. 4 is a block diagram of a content addressable memory (CAM) block implemented within a memory device in accordance with some embodiments of the present disclosure.

FIG. 5 is a flow diagram of an example method of programming content addressable memory (CAM) in a memory sub-system in accordance with some embodiments of the present disclosure.

FIG. 6 is a block diagram of an example computer system in which embodiments of the present disclosure can operate.

DETAILED DESCRIPTION

Aspects of the present disclosure are directed to programming content addressable memory (CAM) in a memory sub-system. A memory sub-system can be a storage device, a memory module, or a hybrid of a storage device and memory module. Examples of storage devices and memory modules are described below in conjunction with FIG. 1. In general, a host system can utilize a memory sub-system that includes one or more components, such as memory devices that store data. The host system can provide data to be stored at the memory sub-system and can request data to be retrieved from the memory sub-system.

A content addressable memory (CAM) is a type of memory device that is often used in certain very high speed searching applications such as identifier (ID) and pattern matching. Generally, a CAM is searched by comparing input search data against a table of stored data entries and a memory address of matching data in the table is returned. CAMs are frequently implemented in dynamic random-access memory (DRAM), or synchronous random-access memory (SRAM). Both DRAM and SRAM, however, have a limited memory capacity, which limits the amount of data that can be stored and searched in conventional CAM implementations.

A memory sub-system can include high density non-volatile memory devices where retention of data is desired when no power is supplied to the memory device. One example of non-volatile memory devices is a negative-and (NAND) memory device. Other examples of non-volatile memory devices are described below in conjunction with FIG. 1. A non-volatile memory device is a package of one or more dies. Each die can consist of one or more planes. For some types of non-volatile memory devices (e.g., NAND devices), each plane consists of a set of physical blocks. Each block consists of a set of pages. Each page consists of a set of memory cells (“cells”). A cell is an electronic circuit that stores information. Depending on the cell type, a cell can store one or more bits of binary information, and has various logic states that correlate to the number of bits being stored. The logic states can be represented by binary values, such as “0” and “1”, or combinations of such values.

A memory device can be made up of bits arranged in a two-dimensional or a three-dimensional grid. Memory cells are etched onto a silicon wafer in an array of columns (also hereinafter referred to as bitlines) and rows (also hereinafter referred to as wordlines). A wordline can refer to one or more rows of memory cells of a memory device that are used with one or more bitlines to generate the address of each of the memory cells. The intersection of a bitline and wordline constitutes the address of the memory cell. A block hereinafter refers to a unit of the memory device used to store data and can include a group of memory cells, a wordline group, a wordline, or individual memory cells. One or more blocks can be grouped together to form a plane of the memory device in order to allow concurrent operations to take place on each plane. The memory device can include circuitry that performs concurrent memory page accesses of two or more memory planes. For example, the memory device can include multiple access line driver circuits and power circuits that can be shared by the planes of the memory device to facilitate concurrent access of pages of two or more memory planes, including different page types. For ease of description, these circuits can be generally referred to as independent plane driver circuits. Depending on the storage architecture employed, data can be stored across the memory planes (i.e., in stripes). Accordingly, one request to read a segment of data (e.g., corresponding to one or more data addresses), can result in read operations performed on two or more of the memory planes of the memory device.

A string is a unit in a NAND-type flash memory device. NAND-type flash memory devices typically have 32 or more memory cells, where each memory cell is used to represent a bit value (e.g., 0 or 1). Thus, a string with 32 memory cells can represent 32 bits of data and a string with 64 memory cells can represent 64 bits of data. In a NAND-type flash memory block, individual strings are connected to allow storage and retrieval of data from selected cells. Typically, strings in the block are connected at one end to a common source line and at the other end to a bit line. Each string also contains two control mechanisms in series with the memory cells. String and ground select transistors are connected to the string select line and ground select line. Memory cells in NAND-type flash components are connected horizontally at their control gates to a word line to form a page. A page is a set of connected memory cells that share the same word line and are the minimum unit to program. NAND-type flash memory devices may have page sizes of 64K or 128K cells. Although conventional NAND-type flash memory has a larger capacity than DRAM and SRAM, it is generally too slow for serial data searching and access.

Thus, in certain implementations, it can be beneficial for a memory sub-system to utilize a CAM architecture implemented in a NAND-type flash memory device to provide both fast and high capacity search capability. Consistent with this architecture, data entries can be stored on strings of a NAND-type flash memory array. A search pattern representing an input search word can be input vertically on each word line corresponding to a string in the array of the CAM. A single read operation compares the input search word (i.e., a search key) with all strings in the selected portion of the array, typically a sub-block in one or more planes, and identifies a storage address of matching data (i.e., a stored key). In order to achieve the performance benefits described herein when searching the CAM, the data entries are stored vertically along a string intersecting multiple wordlines. Thus, each wordline includes portions of many different data entries (i.e., stored keys). When the CAM is implemented in a NAND-type flash memory device, however, programming is performed one wordline at a time. Thus, many different data entries (e.g., 1024 stored keys) must be stored and available when programming any one wordline. To maintain these data entries in a high speed volatile memory, such as DRAM, would be prohibitively expensive given the number of data entries involved.

Aspects of the present disclosure address the above and other deficiencies by providing improved techniques for programming content addressable memory (CAM) in a memory sub-system. The memory sub-system includes a CAM block to be programmed with data entries stored vertically along strings of a NAND-type flash memory array. In one embodiment, the memory sub-system further includes a programming buffer where the data entries can be temporarily stored before being programmed to the CAM block. Depending on the implementation, the programming buffer can be implemented in NAND-type flash memory, or other non-volatile memory, which is not arranged using a CAM architecture. In one embodiment, as data to be stored is received at the memory sub-system (e.g., from a host system), the data can be stored as pages in the programming buffer. Each page can include a certain number of data entries (e.g., 1024 keys). Depending on the size of the programming buffer, the programming buffer can hold a certain number of pages (e.g., 128 pages). Once each page of the programming buffer has been filled with data entries to be stored in the CAM block, a memory sub-system controller can perform a conversion operation to prepare the data for programming to the CAM block. As described in more detail below, the conversion operation effectively rotates the data 90 degrees such that a portion of each key stored in the programming buffer can be written to a given wordline (or set of wordlines) in the CAM block. Each wordline or set of wordlines in the CAM block can be referred to as a CAM page. As a result, each key that was previously maintained in a single page of the programming buffer is now stored in the CAM block vertically along a string intersecting multiple wordlines (i.e., across multiple CAM pages). Once stored in the CAM block, the data entries are quickly and efficiently searchable for comparison to an input search key to identify a match in the CAM block.

Advantages of this approach include, but are not limited to, improved performance in the memory sub-system. Programming the NAND-based CAM architecture can be performed without requiring massive amounts of DRAM to buffer the data entries. This reduces the cost of the memory sub-system, and improves power utilization during the programming operations. Efficiently programming the data entries into a CAM array enables the memory sub-system to be practically used for new applications where high speed and high-density pattern matching is performed, such as applications related to artificial intelligence, machine vision, and large genetic databases. Such a CAM architecture also improves existing database search systems and search algorithms such as index memories in cloud networking and servers.

FIG. 1 illustrates an example computing system 100 that includes a memory sub-system 110 in accordance with some embodiments of the present disclosure. The memory sub-system 110 can include media, such as one or more volatile memory devices (e.g., memory device 140), one or more non-volatile memory devices (e.g., memory device 130), or a combination of such.

A memory sub-system 110 can be a storage device, a memory module, or a hybrid of a storage device and memory module. Examples of a storage device include a solid-state drive (SSD), a flash drive, a universal serial bus (USB) flash drive, an embedded Multi-Media Controller (eMMC) drive, a Universal Flash Storage (UFS) drive, a secure digital (SD) and a hard disk drive (HDD). Examples of memory modules include a dual in-line memory module (DIMM), a small outline DIMM (SO-DIMM), and various types of non-volatile dual in-line memory module (NVDIMM).

The computing system 100 can be a computing device such as a desktop computer, laptop computer, network server, mobile device, a vehicle (e.g., airplane, drone, train, automobile, or other conveyance), Internet of Things (IoT) enabled device, embedded computer (e.g., one included in a vehicle, industrial equipment, or a networked commercial device), or such computing device that includes memory and a processing device.

The computing system 100 can include a host system 120 that is coupled to one or more memory sub-systems 110. In some embodiments, the host system 120 is coupled to different types of memory sub-system 110. FIG. 1 illustrates one example of a host system 120 coupled to one memory sub-system 110. As used herein, “coupled to” or “coupled with” generally refers to a connection between components, which can be an indirect communicative connection or direct communicative connection (e.g., without intervening components), whether wired or wireless, including connections such as electrical, optical, magnetic, etc.

The host system 120 can include a processor chipset and a software stack executed by the processor chipset. The processor chipset can include one or more cores, one or more caches, a memory controller (e.g., NVDIMM controller), and a storage protocol controller (e.g., PCIe controller, SATA controller). The host system 120 uses the memory sub-system 110, for example, to write data to the memory sub-system 110 and read data from the memory sub-system 110.

The host system 120 can be coupled to the memory sub-system 110 via a physical host interface. Examples of a physical host interface include, but are not limited to, a serial advanced technology attachment (SATA) interface, a peripheral component interconnect express (PCIe) interface, universal serial bus (USB) interface, Fibre Channel, Serial Attached SCSI (SAS), a double data rate (DDR) memory bus, Small Computer System Interface (SCSI), a dual in-line memory module (DIMM) interface (e.g., DIMM socket interface that supports Double Data Rate (DDR)), etc. The physical host interface can be used to transmit data between the host system 120 and the memory sub-system 110. The host system 120 can further utilize an NVM Express (NVMe) interface, Open NAND Flash Interface (ONFI) interface, or some other interface to access components (e.g., memory devices 130) when the memory sub-system 110 is coupled with the host system 120 by the physical host interface (e.g., PCIe bus). The physical host interface can provide an interface for passing control, address, data, and other signals between the memory sub-system 110 and the host system 120. FIG. 1 illustrates a memory sub-system 110 as an example. In general, the host system 120 can access multiple memory sub-systems via a same communication connection, multiple separate communication connections, and/or a combination of communication connections.

The memory devices 130, 140 can include any combination of the different types of non-volatile memory devices and/or volatile memory devices. The volatile memory devices (e.g., memory device 140) can be, but are not limited to, random access memory (RAM), such as dynamic random access memory (DRAM) and synchronous dynamic random access memory (SDRAM).

Some examples of non-volatile memory devices (e.g., memory device 130) include negative-and (NAND) type flash memory and write-in-place memory, such as a three-dimensional cross-point (“3D cross-point”) memory device, which is a cross-point array of non-volatile memory cells. A cross-point array of non-volatile memory can perform bit storage based on a change of bulk resistance, in conjunction with a stackable cross-gridded data access array. Additionally, in contrast to many flash-based memories, cross-point non-volatile memory can perform a write in-place operation, where a non-volatile memory cell can be programmed without the non-volatile memory cell being previously erased. NAND type flash memory includes, for example, two-dimensional NAND (2D NAND) and three-dimensional NAND (3D NAND).

Each of the memory devices 130 can include one or more arrays of memory cells. One type of memory cell, for example, single level cells (SLC) can store one bit per cell. Other types of memory cells, such as multi-level cells (MLCs), triple level cells (TLCs), quad-level cells (QLCs), and penta-level cells (PLCs) can store multiple bits per cell. In some embodiments, each of the memory devices 130 can include one or more arrays of memory cells such as SLCs, MLCs, TLCs, QLCs, or any combination of such. In some embodiments, a particular memory device can include an SLC portion, and an MLC portion, a TLC portion, a QLC portion, or a PLC portion of memory cells. The memory cells of the memory devices 130 can be grouped as pages that can refer to a logical unit of the memory device used to store data. With some types of memory (e.g., NAND), pages can be grouped to form blocks.

Although non-volatile memory components such as 3D cross-point array of non-volatile memory cells and NAND type flash memory (e.g., 2D NAND, 3D NAND) are described, the memory device 130 can be based on any other type of non-volatile memory, such as read-only memory (ROM), phase change memory (PCM), self-selecting memory, other chalcogenide based memories, ferroelectric transistor random-access memory (FeTRAM), ferroelectric random access memory (FeRAM), magneto random access memory (MRAM), Spin Transfer Torque (STT)-MRAM, conductive bridging RAM (CBRAM), resistive random access memory (RRAM), oxide based RRAM (OxRAM), negative-or (NOR) flash memory, and electrically erasable programmable read-only memory (EEPROM).

A memory sub-system controller 115 (or controller 115 for simplicity) can communicate with the memory devices 130 to perform operations such as reading data, writing data, or erasing data at the memory devices 130 and other such operations. The memory sub-system controller 115 can include hardware such as one or more integrated circuits and/or discrete components, a buffer memory, or a combination thereof. The hardware can include a digital circuitry with dedicated (i.e., hard-coded) logic to perform the operations described herein. The memory sub-system controller 115 can be a microcontroller, special purpose logic circuitry (e.g., a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), etc.), or other suitable processor.

The memory sub-system controller 115 can be a processing device, which includes one or more processors (e.g., processor 117), configured to execute instructions stored in a local memory 119. In the illustrated example, the local memory 119 of the memory sub-system controller 115 includes an embedded memory configured to store instructions for performing various processes, operations, logic flows, and routines that control operation of the memory sub-system 110, including handling communications between the memory sub-system 110 and the host system 120.

In some embodiments, the local memory 119 can include memory registers storing memory pointers, fetched data, etc. The local memory 119 can also include read-only memory (ROM) for storing micro-code. While the example memory sub-system 110 in FIG. 1 has been illustrated as including the memory sub-system controller 115, in another embodiment of the present disclosure, a memory sub-system 110 does not include a memory sub-system controller 115, and can instead rely upon external control (e.g., provided by an external host, or by a processor or controller separate from the memory sub-system).

In general, the memory sub-system controller 115 can receive commands or operations from the host system 120 and can convert the commands or operations into instructions or appropriate commands to achieve the desired access to the memory devices 130. The memory sub-system controller 115 can be responsible for other operations such as wear leveling operations, garbage collection operations, error detection and error-correcting code (ECC) operations, encryption operations, caching operations, and address translations between a logical address (e.g., logical block address (LBA), namespace) and a physical address (e.g., physical block address) that are associated with the memory devices 130. The memory sub-system controller 115 can further include host interface circuitry to communicate with the host system 120 via the physical host interface. The host interface circuitry can convert the commands received from the host system into command instructions to access the memory devices 130 as well as convert responses associated with the memory devices 130 into information for the host system 120.

The memory sub-system 110 can also include additional circuitry or components that are not illustrated. In some embodiments, the memory sub-system 110 can include a cache or buffer (e.g., DRAM) and address circuitry (e.g., a row decoder and a column decoder) that can receive an address from the memory sub-system controller 115 and decode the address to access the memory devices 130.

In some embodiments, the memory devices 130 include local media controllers 135 that operate in conjunction with memory sub-system controller 115 to execute operations on one or more memory cells of the memory devices 130. An external controller (e.g., memory sub-system controller 115) can externally manage the memory device 130 (e.g., perform media management operations on the memory device 130). In some embodiments, memory sub-system 110 is a managed memory device, which includes a raw memory device 130 having control logic (e.g., local media controller 135) on the die and a controller (e.g., memory sub-system controller 115) for media management within the same memory device package. An example of a managed memory device is a managed NAND (MNAND) device.

In one embodiment, memory device 130 can be configured to include a programming buffer 137 and content addressable memory (CAM) block 139, which can optionally be part of a CAM NAND key-value database. Programming buffer 137 can be used to temporarily store data entries before being programmed to CAM block 139. Depending on the implementation, the programming buffer 137 can be implemented in NAND-type flash memory, or other non-volatile memory, which is not arranged using a CAM architecture. As described in more detail below, the CAM block 139 can include one or more arrays of memory cells organized as strings. Each string stores a data entry and comprises memory cells connected in series between a match line and a page buffer. That is, the CAM block 139 includes multiple match lines and each match line is connected to one of multiple strings in an array. The match lines of the CAM block 139 correspond to bit lines of a NAND block on which the CAM block 139 is implemented. Within a given string, memory cells can be organized as complementary memory cell pairs. Each bit value of the data entry stored by a string is mapped to one of the complementary memory cell pairs in the string. In one embodiment, programming buffer 137 and CAM block 139 are implemented on the same memory die (e.g., memory device 130). In other embodiments, however, programming buffer 137 and CAM block 139 can be located on separate memory devices in memory sub-system 110.

The CAM block 139 can be searched by providing a search pattern as input to search lines of the CAM block 139. The search lines of the CAM block 139 correspond to word lines of the NAND block on which the CAM block 139 is implemented. In one embodiment, the match lines of the CAM block 139 are precharged to facilitate searching. That is, prior to input of the search, a voltage signal is applied to the match lines of the CAM block 139. During a search operation, if the input search word matches any data entry stored by the CAM block 139, one or more matched lines (e.g., match lines corresponding to strings storing the matching data entry) become conductive and discharge a signal in response to the search pattern input at the search lines. If the search word does not match any stored entry, all match lines are non-conductive. Each match line is further connected to a page buffer (e.g., comprises one or more latch circuits) that receives a discharge signal and stores data indicating that matched data is stored along the connected match line.

In one embodiment, memory sub-system 110 further includes a program component 113 that facilitates programming of the CAM block 139. Consistent with some embodiments, the program component 113 is included in the in the memory sub-system controller 115, as shown. For example, the memory sub-system controller 115 can include the processor 117 (e.g., a processing device) configured to execute instructions stored in the local memory 119 for performing the operations of the program component 113 described herein. In some embodiments, memory device 130 includes at least a portion of the program component 113. In some embodiments, the program component 113 is part of the host system 120, an application, or an operating system.

In one embodiment, as data to be stored is received at memory sub-system 110 (e.g., from host system 120 or some other source), program component 113 can initially store the data as pages in the programming buffer 137. If multiple data entries (e.g., search keys) are received individually, program component 113 can coalesce those entries into a single page, with each page including a certain number of data entries (e.g., 1024 keys). Program component 113 can continue storing received data in programming buffer 137 until programming buffer 137 is full. Depending on the size of the programming buffer 137, the programming buffer 137 can hold a certain number of pages (e.g., 128 pages). Once each page of the programming buffer 137 has been filled with data entries to be stored in the CAM block 139, program component 113 can perform a conversion operation to prepare the data for programming to the CAM block 139. In one embodiment, program component 113 reads a first portion of each stored key from programming buffer 137 and writes those portions to a first wordline (or set of wordlines) of CAM block 139. Program component 113 repeats this process to read a second portion of each stored key from programming buffer 137 and write those portions to a second wordline (or set of wordlines) of CAM block 139, and so on, until all portions of each stored key have been programmed to CAM block 139. As a result, each key that was previously maintained in a single page of the programming buffer 137 is now stored in the CAM block 139 vertically along a string intersecting multiple wordlines (i.e., across multiple CAM pages). Further details with regards to the operations and structure of search component 113, programming buffer 137 and CAM block 139 are described below.

FIG. 2 is a simplified block diagram of a first apparatus, in the form of a memory device 130, in communication with a second apparatus, in the form of a memory sub-system controller 115 of a memory sub-system (e.g., memory sub-system 110 of FIG. 1), according to an embodiment. Some examples of electronic systems include personal computers, personal digital assistants (PDAs), digital cameras, digital media players, digital recorders, games, appliances, vehicles, wireless devices, mobile telephones and the like. The memory sub-system controller 115 (e.g., a controller external to the memory device 130), may be a memory controller or other external host device.

Memory device 130 includes an array of memory cells 250 logically arranged in rows and columns. Memory cells of a logical row are typically connected to the same access line (e.g., a word line) while memory cells of a logical column are typically selectively connected to the same data line (e.g., a bit line). A single access line may be associated with more than one logical row of memory cells and a single data line may be associated with more than one logical column. Memory cells (not shown in FIG. 2) of at least a portion of array of memory cells 250 are capable of being programmed to one of at least two target data states. In one embodiment, the array of memory cells 250 includes programming buffer 137 and CAM block 139. As described herein, the CAM block 139 includes a number of storage keys stored vertically in strings to which a received search key can be compared. When a match is determined, the location of the matching storage key in CAM block 139 points to a location of corresponding values in a value data block (not shown) which can be retrieved and returned to the requestor. In one embodiment, memory device 130 organized into multiple planes. In one embodiment, for example, memory device 130 includes four planes. In other embodiments, there can be more or fewer planes, however. Each of the planes can be configured to include one or more programming buffers 137 and CAM blocks 139.

Row decode circuitry 208 and column decode circuitry 210 are provided to decode address signals. Address signals are received and decoded to access the array of memory cells 250. Memory device 130 also includes input/output (I/O) control circuitry 212 to manage input of commands, addresses and data to the memory device 130 as well as output of data and status information from the memory device 130. An address register 214 is in communication with I/O control circuitry 212 and row decode circuitry 208 and column decode circuitry 210 to latch the address signals prior to decoding. A command register 224 is in communication with I/O control circuitry 212 and local media controller 135 to latch incoming commands.

A controller (e.g., the local media controller 135 internal to the memory device 130) controls access to the array of memory cells 250 in response to the commands and generates status information for the external memory sub-system controller 115, i.e., the local media controller 135 is configured to perform access operations (e.g., read operations, programming operations and/or erase operations) on the array of memory cells 250. The local media controller 135 is in communication with row decode circuitry 208 and column decode circuitry 210 to control the row decode circuitry 208 and column decode circuitry 210 in response to the addresses.

The local media controller 135 is also in communication with a cache register 242. Cache register 242 latches data, either incoming or outgoing, as directed by the local media controller 135 to temporarily store data while the array of memory cells 250 is busy writing or reading, respectively, other data. During a program operation (e.g., write operation), data may be passed from the cache register 242 to the data register 244 for transfer to the array of memory cells 250; then new data may be latched in the cache register 242 from the I/O control circuitry 212. During a read operation, data may be passed from the cache register 242 to the I/O control circuitry 212 for output to the memory sub-system controller 115; then new data may be passed from the data register 244 to the cache register 242. The cache register 242 and/or the data register 244 may form (e.g., may form a portion of) a page buffer of the memory device 130. A page buffer may further include sensing devices (not shown in FIG. 2) to sense a data state of a memory cell of the array of memory cells 250, e.g., by sensing a state of a data line connected to that memory cell. A status register 222 may be in communication with I/O control circuitry 212 and the local memory controller 135 to latch the status information for output to the memory sub-system controller 115.

Memory device 130 receives control signals at the memory sub-system controller 115 from the local media controller 135 over a control link 232. For example, the control signals can include a chip enable signal CE #, a command latch enable signal CLE, an address latch enable signal ALE, a write enable signal WE #, a read enable signal RE #, and a write protect signal WP #. Additional or alternative control signals (not shown) may be further received over control link 232 depending upon the nature of the memory device 130. In one embodiment, memory device 130 receives command signals (which represent commands), address signals (which represent addresses), and data signals (which represent data) from the memory sub-system controller 115 over a multiplexed input/output (I/O) bus 234 and outputs data to the memory sub-system controller 115 over I/O bus 234.

For example, the commands may be received over input/output (I/O) pins [7:0] of I/O bus 234 at I/O control circuitry 212 and may then be written into command register 224. The addresses may be received over input/output (I/O) pins [7:0] of I/O bus 234 at I/O control circuitry 212 and may then be written into address register 214. The data may be received over input/output (I/O) pins [7:0] for an 8-bit device or input/output (I/O) pins [15:0] for a 16-bit device at I/O control circuitry 212 and then may be written into cache register 242. The data may be subsequently written into data register 244 for programming the array of memory cells 250.

In an embodiment, cache register 242 may be omitted, and the data may be written directly into data register 244. Data may also be output over input/output (I/O) pins [7:0] for an 8-bit device or input/output (I/O) pins [15:0] for a 16-bit device. Although reference may be made to I/O pins, they may include any conductive node providing for electrical connection to the memory device 130 by an external device (e.g., the memory sub-system controller 115), such as conductive pads or conductive bumps as are commonly used.

It will be appreciated by those skilled in the art that additional circuitry and signals can be provided, and that the memory device 130 of FIG. 2 has been simplified. It should be recognized that the functionality of the various block components described with reference to FIG. 2 may not necessarily be segregated to distinct components or component portions of an integrated circuit device. For example, a single component or component portion of an integrated circuit device could be adapted to perform the functionality of more than one block component of FIG. 2. Alternatively, one or more components or component portions of an integrated circuit device could be combined to perform the functionality of a single block component of FIG. 2. Additionally, while specific I/O pins are described in accordance with popular conventions for receipt and output of the various signals, it is noted that other combinations or numbers of I/O pins (or other I/O node structures) may be used in the various embodiments.

FIG. 3 is a block diagram illustrating programming content addressable memory (CAM) in a memory sub-system, according to an embodiment. FIG. 3 illustrates an embodiment where memory device 130 includes both programming buffer 137 and CAM block 139. It should be appreciated, however, that in other embodiments, programming buffer 137 and CAM block 139 can be implemented on separate memory devices within memory sub-system 110.

In one embodiment, as data to be stored is received at memory sub-system 110 (e.g., from host system 120 or some other source), program component 113 can initially store the data as pages in the programming buffer 137. Depending on the size of the programming buffer 137, the programming buffer 137 can hold a certain number m of pages (i.e., page0-page m-1). Each page of programming buffer 137 can store a certain number n of stored keys. For example, page0 can store key0-keyn-1, page 1 can store keyn-key(n-1)*2, and so on up to pagem-1, which can store keyn*m-key(n-1)*(m-1). If multiple keys are received individually, program component 113 can coalesce those entries into a single page which is written to programming buffer 137. Program component 113 can continue storing received keys as pages in programming buffer 137 until programming buffer 137 is full. Programming buffer 137 enables individual keys to be stored temporarily until they can be programmed to CAM block 139, as will be described below. In other embodiments, programming buffer 137 can include some other number of pages and each page can include some other number of keys.

Once each page (i.e., page0-pagem-1) of the programming buffer 137 has been filled with keys, program component 113 can perform a conversion operation 310 to prepare the data for programming to the CAM block 139. The conversion operation 310 effectively rotates the data 90 degrees such that a portion of each key stored in the programming buffer 137 can be written to a given wordline (or set of wordlines) in the CAM block 139. In one embodiment, program component 113 reads a first portion of each stored key from programming buffer 137 and writes those portions to a first wordline (or set of wordlines) of CAM block 139. For example, program component 113 can read portion 301 of key0, portion 304 of key1, and so on, up to portion 307 of key(n-1)*(m-1) and program those portions 301, 304, up to 307 to a single page of CAM block 139 (e.g., CAM page0). In one embodiment, each CAM page includes a pair of wordlines in CAM bock 139 with one wordline of the pair including memory cells storing the true values from portions 301, 304, up to 307, and the other wordline of the pair including memory cells storing the complement of those values.

In one embodiment, program component 113 repeats this process to read a second portion of each stored key from programming buffer 137 and write those portions to a second wordline (or set of wordlines) of CAM block 139, and so on, until all portions of each stored key have been programmed to CAM block 139. For example, program component 113 can read portion 302 of key0, portion 305 of key1, and so on, up to portion 308 of key(n-1)*(m-1) and program those portions 302, 305, up to 308 to CAM page1, and can read portion 303 of key0, portion 306 of key1, and so on, up to portion 309 of key(n-1)*(m-1) and program those portions 303, 306, up to 309 to CAM pagem-1. As a result, each key that was previously maintained in a single page of the programming buffer 137 is now stored in the CAM block 139 vertically along a string intersecting multiple wordlines (i.e., across multiple CAM pages). For example, the corresponding portions of each of keys key0-key(n-1)*(m-1) can be spread across CAM page0-CAM pagem-1.

Once programed, CAM block 139 can be searched to detect the presence of a stored key matching an input search key. In one embodiment, memory sub-system controller 115 receives an input search key (e.g., a search word) and applies the input search key to CAM block 139 to compare the input search key to the stored search keys. In one embodiment, the memory sub-system controller 115 generates a search pattern based on the input search ley. The input search key can include a first sequence of bits (e.g., “1011”). The generated search pattern can include a first set of voltage signals representing the input search key and a second set of voltage signals representing a second sequence of bits comprising an inverse of the first sequence of bits (e.g., “0100”). In one embodiment, memory sub-system controller 115 includes an inverter to generate an inverse of the input search key and a level selector to generate the first and second signals. In generating the first and second voltage signals, the level selector can use a high voltage to represent a binary value of “1” and use a low voltage to represent a binary value of “0” where the high voltage is above a threshold voltage (Vt) and the low voltage is below Vt.

To search CAM block 139, memory sub-system controller 115 inputs the search key (i.e., the representative search pattern) vertically along search lines of the CAM block 139. Input of the search key causes any complementary memory cell pairs representing a matching stored bit value to become conductive. If a string is storing matching data (i.e. a matching one of the stored search keys), the entire string becomes conductive. Match lines in the CAM block 139 are precharged (e.g., connected to the high voltage), and because the match lines are precharged, input of the search key on the search lines causes any match lines in the block that are storing matching data (e.g., one of the stored search keys that is identical to the input search key) to output a discharge signal because the corresponding string is conductive. The discharge signal provides an indication that matching data (e.g., the input search key) is stored thereon. The discharge signal provides an indication that matching data is stored on the string connected to the match line.

Each string is connected between a match line and a page buffer (e.g., comprising one or more latch circuits) and the page buffer of a matched line stores data indicating matching data is stored along the matched line in response to the signal provided as a result of the match line discharging along the string. A page buffer can include one or more latch circuits. Physically, the page buffer(s) reside under or adjacent to the arrays of memory cells in which CAM block(s) 139 are implemented. A page buffer latches data based on the signal provided by a matched line when matching data is stored by the connected string that conducts the signal to the page buffer. The memory sub-system controller 115 reads data from the page buffer(s) and provides an indicator of whether the input search key 310 is stored in CAM block 139 being searched as output along with a match location (e.g., a memory address of the string in the array).

In some embodiments, the memory sub-system controller 115 can sequentially search for matching data in the CAM block(s) 139 of multiple memory planes. In some embodiments, the memory sub-system controller 115 can search for matching data in the CAM block(s) 139 of the multiple memory planes in parallel. Parallel searching of the multiple memory planes allows all data entries stored among all CAM block(s) 139 of the planes to be searched in a single search operation rather than completing the search of all data entries in four separate search operations. Hence, parallel searching, as utilized in the embodiments described above, can allow the memory sub-system controller 115 to achieve an increase to search speed relative to embodiments in which sequential searching is utilized.

In some embodiments, data entries can be stored across two or more of the memory planes. In these instances, the memory sub-system controller 115 can simultaneously search for portions of matching data across two or more of the memory planes. Dividing data entries across planes allows for greater word size when compared to embodiments in which data entries are stored within a single plane. For example, if each of the CAM blocks 139 supports 64-bit words, dividing the data entries among all four planes would allow the memory device to support 256-bit words (4*64=256).

FIG. 4 is a block diagram of a content addressable memory (CAM) block implemented within a memory device in accordance with some embodiments of the present disclosure. As shown, the CAM block 139 includes match lines 402-0 to 402-N, search lines 404-0 to 404-M, and inverse search lines 406-0 to 406-M. In this implementation, the match lines 402-0 to 402-N of the CAM block 139 correspond to bit lines of the NAND-type flash memory device and the search lines 404-0 to 404-M and inverse search lines 406-0 to 406-M of the CAM block 139 correspond to word lines of the NAND-type flash memory device.

Each of the match lines 402-0 to 402-N is connected to a string comprising a plurality of memory cells connected in series. For example, match line 402-0 is connected to a string comprising memory cells 408-0 to 408-X, where X=2M. Memory cells in each string of the CAM block 139 are configured to be complementary pairs. For example, with the string connected to match line 402-0, memory cells 408-0 to 408-X are programmed as complementary memory cell pairs 410-0 to 410-M.

Memory cell pairs are configured to be complementary in that one memory cell in the pair stores a data value (“0”) and the other memory cell in the pair stores an inverse of the data value (“1”). For example, memory cell pair 410-0 comprises two memory cells. A first memory cell stores a data bit value DATA, and a second memory cell 408-0 stores DATA, which is an inverse of the data bit value DATA. Also, as shown, search line 404-0 is connected to a control gate of the first memory cell and inverse search line 406-0 is connected to a control gate of the second memory cell.

Search line 404-0 receives a first signal SL representing a search bit value from an input search word and inverse search line 406-0 receives a second signal SL representing an inverse of the search bit value. If SL matches DATA and SL matches DATA, the memory cell pair 410-0 will be conductive from A to B. For example, TABLE 1 provided below is a truth table that defines the behavior of any given one of the memory cell pairs 410-0 to 410-M.

TABLE 1 SL SL DATA DATA CONDUCTIVE 0 1 0 1 YES 0 1 1 0 NO 1 0 0 1 NO 1 0 1 0 YES

In TABLE 1, “SL” is a search bit value, “SL” is an inverse of the search bit value, “DATA” is a stored bit value, and “DATA” is an inverse of the stored bit value. As shown, a complementary cell pair is conductive when the search data value matches the stored data value and the inverse of the search data value matches the inverse of the stored data value. I n other instances, the memory cell pair 410 is non-conductive because the stored data does not match the search bit.

In one embodiment, each string in the CAM block 139 stores a data entry and each data bit value in a data entry is mapped to one of the memory cell pairs 410-0 to 410-M in the string. In this way, within each of the complementary memory cell pairs 410 in a string, a first memory cell stores a bit value from the data entry and a second memory cell stores an inverse of the bit value from the data entry.

In an example where the NAND-type flash memory device supports 128 bit strings (i.e., X is 128), the match line 402-0 is connected to memory cells 408-0 to 408-127, which stores 64 bit data entry comprising bit values D_(0,0)-D_(63,63). In this example, bit value D_(0,0) is mapped to memory cell pair 410-0 comprising memory cells 408-0 and 408-1. More specifically, memory cell 408-0 stores the bit value D_(0,0) and the complementary memory cell stores D _(0,0), which is the inverse of the bit value D_(0,0).

A search pattern 420 may be input vertically along search lines 404-0 to 404-M and inverse search lines 406-0 to 406-M. More specifically, search lines 404-0 to 404-M receive a first set of voltage signals SL_(0-M) representing a search word 420, and inverse search lines 406-0 to 406-M receive a second set of voltage signals SL _(0-M) representing an inverse of the search word. Input of the search pattern 420 along the search lines causes any string that stores matching data to be conductive because, as discussed above, each individual memory cell pair 410 in the string will be conductive. Because the match lines 402 are precharged, a conductive string allows the match line 402 to discharge. A page buffer connected to a conductive string latches data that indicates a location of matching data (i.e., the search word) in the CAM block 139.

The memory sub-system controller 115 outputs an indication of whether a search word is stored by the CAM block 139 and an indicator of the location (e.g., a memory address) of the matching data. In some embodiments, the memory sub-system controller 115 comprises a read-out circuit that reads data from the page buffers of the CAM block 139 to identify the location thereof.

In some embodiments, two page buffers in the CAM block 139 can be tied together to form a serial shift register. Consistent with these embodiments, the memory sub-system controller 115 shifts data out of a first page buffer to a second page buffer and the memory sub-system controller 115 comprises an output compare and counter component to track the number of shifts from one page buffer to the other to identify the location of matching data stored by the CAM block 139. In some embodiments, two page buffers may be tied together using a single transistor to form a shift register.

FIG. 5 is a flow diagram of an example method of programming content addressable memory (CAM) in a memory sub-system in accordance with some embodiments of the present disclosure. The method 500 can be performed by processing logic that can include hardware (e.g., processing device, circuitry, dedicated logic, programmable logic, microcode, hardware of a device, integrated circuit, etc.), software (e.g., instructions run or executed on a processing device), or a combination thereof. In some embodiments, the method 500 is performed by program component 113 of FIG. 1. Although shown in a particular sequence or order, unless otherwise specified, the order of the processes can be modified. Thus, the illustrated embodiments should be understood only as examples, and the illustrated processes can be performed in a different order, and some processes can be performed in parallel. Additionally, one or more processes can be omitted in various embodiments. Thus, not all processes are required in every embodiment. Other process flows are possible.

At operation 505, data entries are received. For example, processing logic (e.g., program component 113) can receive the data entries (e.g., search keys) from a requestor (e.g., host system 120). In one embodiment, each data entry includes a respective sequence of bits (e.g., “1001 1010 1011”).

At operation 510, data entries are stored. For example, the processing logic can store the data entries in the pages (e.g., page0-pagem-1) of a programming buffer (e.g., programming buffer 137). Depending on the size of the programming buffer 137, the programming buffer 137 can hold a certain number m of pages. Each page of programming buffer 137 can store a certain number n of data entries, which represents a respective subset of the received data entries. If multiple data entries are received individually, program component 113 can coalesce those entries which are written together as a single page to programming buffer 137.

At operation 515, a determination is made. For example, the processing logic can determine whether the programming buffer 137 is full of data entries. In one embodiment, the programming buffer 137 is full when each page (e.g., page0-pagem-1) has been fully written with data entries and there is no capacity to store additional data entries. In another embodiment, some other threshold criterion is defined, and the processing logic determines that the programming buffer 137 is full when that threshold criterion is satisfied.

If it is determined that the programming buffer 137 is not full (e.g., the threshold criterion is not satisfied), processing can return to operations 505 and 510 and the processing logic can continue storing received data entries as pages in programming buffer 137 until programming buffer 137 is full. If, however, it is determined that the programming buffer 137 is fill, at operation 520, a conversion operation is initiated. For example, the processing logic can perform the conversion operation to copy the data entries from the programming buffer 137 to the CAM block 139. The conversion operation effectively rotates the data entries 90 degrees such that a portion of each data entry stored in the programming buffer 137 can be written to a given wordline (or set of wordlines) in the CAM block 139.

At operation 525, portions of data are read. For example, the processing device can read respective portions of each data entry in each respective subset of the data entries from the pages of the programming buffer 127. In one embodiment, program component 113 reads a first portion of each stored data entry from programming buffer 137. For example, program component 113 can read portion 301 of key0, portion 304 of key1, and so on, up to portion 307 of key(n-1)*(m-1).

At operation 530, portions of data are written. For example, the processing device can write the respective portions of each data entry to respective CAM pages of the CAM block 139. In one embodiment, program component 113 can program portions 301, 304, up to 307 to a single page of CAM block 139 (e.g., CAM page0). In one embodiment, each CAM page includes a pair of wordlines in CAM bock 139 with one wordline of the pair including memory cells storing the true values from portions 301, 304, up to 307, and the other wordline of the pair including memory cells storing the complement of those values. In one embodiment, program component 113 repeats this process to read a second portion of each stored data entry from programming buffer 137 and write those portions to a second wordline (or set of wordlines) of CAM block 139, and so on, until all portions of each stored data entry have been programmed to CAM block 139. As a result, each data entry that was previously maintained in a single page of the programming buffer 137 is now stored in the CAM block 139 vertically along a string intersecting multiple wordlines (i.e., across multiple CAM pages).

FIG. 6 illustrates an example machine of a computer system 600 within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, can be executed. In some embodiments, the computer system 600 can correspond to a host system (e.g., the host system 120 of FIG. 1) that includes, is coupled to, or utilizes a memory sub-system (e.g., the memory sub-system 110 of FIG. 1) or can be used to perform the operations of a controller (e.g., to execute an operating system to perform operations corresponding to program component 113 of FIG. 1). In alternative embodiments, the machine can be connected (e.g., networked) to other machines in a LAN, an intranet, an extranet, and/or the Internet. The machine can operate in the capacity of a server or a client machine in client-server network environment, as a peer machine in a peer-to-peer (or distributed) network environment, or as a server or a client machine in a cloud computing infrastructure or environment.

The machine can be a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a cellular telephone, a web appliance, a server, a network router, a switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.

The example computer system 600 includes a processing device 602, a main memory 604 (e.g., read-only memory (ROM), flash memory, dynamic random access memory (DRAM) such as synchronous DRAM (SDRAM) or Rambus DRAM (RDRAM), etc.), a static memory 606 (e.g., flash memory, static random access memory (SRAM), etc.), and a data storage system 618, which communicate with each other via a bus 630.

Processing device 602 represents one or more general-purpose processing devices such as a microprocessor, a central processing unit, or the like. More particularly, the processing device can be a complex instruction set computing (CISC) microprocessor, reduced instruction set computing (RISC) microprocessor, very long instruction word (VLIW) microprocessor, or a processor implementing other instruction sets, or processors implementing a combination of instruction sets. Processing device 602 can also be one or more special-purpose processing devices such as an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a digital signal processor (DSP), network processor, or the like. The processing device 602 is configured to execute instructions 626 for performing the operations and steps discussed herein. The computer system 600 can further include a network interface device 608 to communicate over the network 620.

The data storage system 618 can include a machine-readable storage medium 624 (also known as a computer-readable medium, such as a non-transitory computer-readable medium) on which is stored one or more sets of instructions 626 or software embodying any one or more of the methodologies or functions described herein. The instructions 626 can also reside, completely or at least partially, within the main memory 604 and/or within the processing device 602 during execution thereof by the computer system 600, the main memory 604 and the processing device 602 also constituting machine-readable storage media. The machine-readable storage medium 624, data storage system 618, and/or main memory 604 can correspond to the memory sub-system 110 of FIG. 1.

In one embodiment, the instructions 626 include instructions to implement functionality corresponding to program controller 113 of FIG. 1). While the machine-readable storage medium 624 is shown in an example embodiment to be a single medium, the term “machine-readable storage medium” should be taken to include a single medium or multiple media that store the one or more sets of instructions. The term “machine-readable storage medium” shall also be taken to include any medium that is capable of storing or encoding a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the present disclosure. The term “machine-readable storage medium” shall accordingly be taken to include, but not be limited to, solid-state memories, optical media, and magnetic media.

Some portions of the preceding detailed descriptions have been presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the ways used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of operations leading to a desired result. The operations are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.

It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. The present disclosure can refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage systems.

The present disclosure also relates to an apparatus for performing the operations herein. This apparatus can be specially constructed for the intended purposes, or it can include a general purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program can be stored in a computer readable storage medium, such as, but not limited to, any type of disk including floppy disks, optical disks, CD-ROMs, and magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, or any type of media suitable for storing electronic instructions, each coupled to a computer system bus.

The algorithms and displays presented herein are not inherently related to any particular computer or other apparatus. Various general purpose systems can be used with programs in accordance with the teachings herein, or it can prove convenient to construct a more specialized apparatus to perform the method. The structure for a variety of these systems will appear as set forth in the description below. In addition, the present disclosure is not described with reference to any particular programming language. It will be appreciated that a variety of programming languages can be used to implement the teachings of the disclosure as described herein.

The present disclosure can be provided as a computer program product, or software, that can include a machine-readable medium having stored thereon instructions, which can be used to program a computer system (or other electronic devices) to perform a process according to the present disclosure. A machine-readable medium includes any mechanism for storing information in a form readable by a machine (e.g., a computer). In some embodiments, a machine-readable (e.g., computer-readable) medium includes a machine (e.g., a computer) readable storage medium such as a read only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory components, etc.

In the foregoing specification, embodiments of the disclosure have been described with reference to specific example embodiments thereof. It will be evident that various modifications can be made thereto without departing from the broader spirit and scope of embodiments of the disclosure as set forth in the following claims. The specification and drawings are, accordingly, to be regarded in an illustrative sense rather than a restrictive sense. 

What is claimed is:
 1. A system comprising: a memory device comprising a programming buffer and a content addressable memory (CAM) block; and a processing device, operatively coupled with the memory device, to perform operations comprising: receiving a plurality of data entries to be stored at the memory device; storing the plurality of data entries in a plurality of pages of the programming buffer, each of the plurality of pages of the programming buffer comprising a respective subset of the plurality of data entries; and initiating a conversion operation to copy the plurality of data entries from the programming buffer to the CAM block, wherein the conversion operation comprises: reading respective portions of each data entry in each respective subset of the plurality of data entries from the plurality of pages of the programming buffer; and writing the respective portions to respective CAM pages of the CAM block.
 2. The system of claim 1, wherein the conversion operation further comprises: reading a first portion of each data entry in each respective subset of the plurality of data entries from the plurality of pages of the programming buffer; and writing the first portion of each data entry to a first CAM page of the CAM block.
 3. The system of claim 1, wherein the CAM block comprises an array of memory cells organized into a plurality of strings, each string comprising a plurality of memory cells connected in series between a precharged match line and a page buffer, and wherein each of the plurality of memory cells is connected to one of a plurality of search lines.
 4. The system of claim 3, wherein each respective CAM page of the CAM block is associated with a respective one of the plurality of search lines.
 5. The system of claim 3, wherein once each portion of a given data entry is written to the respective CAM pages of the CAM block, the given data entry is stored in the CAM block along one of the plurality of strings intersecting each of the plurality of search lines.
 6. The system of claim 1, wherein the processing device is to perform operations further comprising: determining that the programming buffer is full of data entries; and responsive to determining that the programming buffer is full of data entries, initiating the conversion operation.
 7. The system of claim 1, wherein the memory device comprises a negative and (NAND) type flash memory device, and wherein the programming buffer is not arranged using a CAM architecture.
 8. A method comprising: receiving a plurality of data entries to be stored at a memory device comprising a programming buffer and a content addressable memory (CAM) block; storing the plurality of data entries in a plurality of pages of the programming buffer, each of the plurality of pages of the programming buffer comprising a respective subset of the plurality of data entries; and initiating a conversion operation to copy the plurality of data entries from the programming buffer to the CAM block, wherein the conversion operation comprises: reading respective portions of each data entry in each respective subset of the plurality of data entries from the plurality of pages of the programming buffer; and writing the respective portions to respective CAM pages of the CAM block.
 9. The method of claim 8, wherein the conversion operation further comprises: reading a first portion of each data entry in each respective subset of the plurality of data entries from the plurality of pages of the programming buffer; and writing the first portion of each data entry to a first CAM page of the CAM block.
 10. The method of claim 8, wherein the CAM block comprises an array of memory cells organized into a plurality of strings, each string comprising a plurality of memory cells connected in series between a precharged match line and a page buffer, and wherein each of the plurality of memory cells is connected to one of a plurality of search lines.
 11. The method of claim 10, wherein each respective CAM page of the CAM block is associated with a respective one of the plurality of search lines.
 12. The method of claim 10, wherein once each portion of a given data entry is written to the respective CAM pages of the CAM block, the given data entry is stored in the CAM block along one of the plurality of strings intersecting each of the plurality of search lines.
 13. The method of claim 8, further comprising: determining that the programming buffer is full of data entries; and responsive to determining that the programming buffer is full of data entries, initiating the conversion operation.
 14. The method of claim 8, wherein the memory device comprises a negative and (NAND) type flash memory device, and wherein the programming buffer is not arranged using a CAM architecture.
 15. A non-transitory machine readable storage medium storing instructions that, when executed by a processing device, cause the processing device to perform operations comprising: receiving a plurality of data entries to be stored at a memory device comprising a programming buffer and a content addressable memory (CAM) block; storing the plurality of data entries in a plurality of pages of the programming buffer, each of the plurality of pages of the programming buffer comprising a respective subset of the plurality of data entries; and initiating a conversion operation to copy the plurality of data entries from the programming buffer to the CAM block, wherein the conversion operation comprises: reading respective portions of each data entry in each respective subset of the plurality of data entries from the plurality of pages of the programming buffer; and writing the respective portions to respective CAM pages of the CAM block.
 16. The non-transitory machine readable storage medium of claim 15, wherein the conversion operation further comprises: reading a first portion of each data entry in each respective subset of the plurality of data entries from the plurality of pages of the programming buffer; and writing the first portion of each data entry to a first CAM page of the CAM block.
 17. The non-transitory machine readable storage medium of claim 15, wherein the CAM block comprises an array of memory cells organized into a plurality of strings, each string comprising a plurality of memory cells connected in series between a precharged match line and a page buffer, and wherein each of the plurality of memory cells is connected to one of a plurality of search lines.
 18. The non-transitory machine readable storage medium of claim 17, wherein each respective CAM page of the CAM block is associated with a respective one of the plurality of search lines.
 19. The non-transitory machine readable storage medium of claim 17, wherein once each portion of a given data entry is written to the respective CAM pages of the CAM block, the given data entry is stored in the CAM block along one of the plurality of strings intersecting each of the plurality of search lines.
 20. The non-transitory machine readable storage medium of claim 15, wherein the memory device comprises a negative and (NAND) type flash memory device, and wherein the programming buffer is not arranged using a CAM architecture. 